home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Atari Mega Archive 1
/
Atari Mega Archive - Volume 1.iso
/
lists
/
gem
/
l_0799
/
563
< prev
next >
Wrap
Internet Message Format
|
1994-08-27
|
2KB
From: s.sanders2@genie.geis.com
Date: Tue, 21 Jun 94 05:57:00 UTC
To: gem-list@world.std.com
Subject: Re: Just an idea...
X-Genie-Id: 4181386
X-Genie-From: S.SANDERS2
Precedence: bulk
Reply: Item #2899169 from GEM-LIST-APPROVAL@WORLD.STD.COM@INET00#
Rick Flashman:
I think using ALT at all is a bad idea. Atari has already nixed it
for use in key combos. Even though Atari hasn't gone to the trouble
of setting enough standards I strongly believe the ones they set
shouldn't be ignored because historically developers really _do_
support their standards soon after being released. The ALT key is a
good example. Shortly after they started stressing that it shouldn't
be used, most programs started using CTRL like they should have.
The idea of the standard is to _recommend_ a selection of
equivalents. Programs like terminal programs shouldn't even be
considered when reserving keys because they emulate other platforms
(and their keys). Terminal program makers need to decide for
themselves how to coalesce the two gracefully.
To All:
I suggest that we don't dillute this discussion further by adding
layers to the original proposal such as specialized key equivalents
and other matters. There is nothing wrong with a v2.0 later so long
as it doesn't change what's in v1.0.
I assume that by the time this discussion is over that we will have
two things:
1. A method that allows applications to consult a global list of
user-defined key equivalents.
2. A standard (base file maybe) that comes as the default for the
above. Beyond that the user is free to confuse himself.
Let's focus a little more. Please.
Is there some way (automated) that we could vote on the current
standard one key at a time (keep/redefine/dont define/discuss) just
once. That might allow us to focus on a couple of problem areas.
On another matter, I think a standard key to force screen redraw is
pretty unnecessary. The only correctly written GEM app that should
need this is one that allows the redraw process to get cut off on
purpose and the redraw should be redone if the user clicks a slider.
MultiTOS provides a way to deal with poorly written apps by having
the AE_SREDRAW and AE_TREDRAW environment variables.
Also, someone complained about using environment variables because
_every_ application gets passed them. I think you're confusing the
global set with the AES's copy. Any system configuration stuff goes
there and goes there once.
-Scott @ SDS